Scoring data flow characteristics to assign data flows to storage systems in a data storage infrastructure for a communication network

ABSTRACT

A data storage infrastructure is disclosed for a communication network that produces a plurality of data flows of network data. The data storage infrastructure comprises a plurality of data storage systems and a storage management system. The data storage systems are configured to store the network data. The storage management system is configured to identify characteristics for the data flows, score the characteristics for the data flows, and process the scores to assign individual ones of the data flows to individual ones of the data storage systems.

RELATED APPLICATIONS

Not applicable

FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable

MICROFICHE APPENDIX

Not applicable

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention is related to the field of communications, and inparticular, to the management of data storage systems for acommunication network.

2. Description of the Prior Art

A communication network provides various communication services tonetwork users. A few examples of communication networks include publicswitched networks, wireless access networks, and Internet networks. Afew examples of communication services include voice communications,data transfer, video delivery, and Internet access.

The operation of a communication network produces vast quantities ofdata that need to be stored. To provide the data storage, thecommunications network includes a storage infrastructure that includes awide array of storage equipment and software. Typically, the storageequipment and software are provided by a diverse set of suppliers. Eachsupplier has their own management system for their products.Unfortunately, the result is a complex set of storage equipment andsoftware with numerous individual management systems. In a largecommunication network, this type of complex storage infrastructure isdifficult and expensive to manage.

The communication network also employs various personnel to plan,deploy, and operate the storage infrastructure. The complexity of thestorage infrastructure is often reflected in a complex set of personnelthat are responsible for various aspects of the storage infrastructure.In such a complex personnel organizational structure, some importantstorage tasks may be under-worked, while less important tasks may beoverworked, or worse, redundantly performed by overlappingorganizations.

The result of this complex storage infrastructure is often wastedexpense and inefficiency. The management of the storage infrastructureand personnel in a communication network has not developed anysystematic approach that decreases cost and improves efficiency.Improved tools for managing storage infrastructures and personnel areneeded.

For example, when the communication network produces a new data flow forstorage, the selection of the appropriate storage system for data may beuninformed. Storage personnel may not properly consider all factorsbefore making the selection. A typical result is that less importantdata uses up capacity on the best storage system, when that capacityshould be reserved for more important data.

In another example, the storage infrastructure typically develops overtime in terms of personnel and technology. Decisions regarding whichtechnology to deploy are often made without a clear and detailed view ofwhat technology is most needed. Thus, the decisions regarding thedeployment of new technology in the complex storage infrastructure areoften uninformed decisions. Likewise, decisions regarding whichpersonnel to deploy are often made without a clear and detailed view ofwhat is most needed. New tools are needed to improve decision makingrelated to how new personnel and technology are utilized.

In another example, the storage infrastructure may become vary large andcomplex. The size and complexity of the infrastructure results inmassive costs. The ability to analyze these massive costs to ensure areturn on investment is difficult. Effective cost models are needed toallow the analysis of costs at various levels and perspectives.

In another example, the storage infrastructure may require a largeemployee base with various skills and tasks. The size and complexity ofthe employee base can make it difficult to decide how to use theemployees. Effective employee models are needed to allow the analysis ofemployee effectiveness at various levels and perspectives.

In another example, the storage infrastructure may require a vast amountof equipment and software. The size and complexity of the infrastructurecan make it difficult to track and maintain the equipment and softwarein the infrastructure. Effective infrastructure models are needed totrack the components of the storage infrastructure.

In another example, the storage infrastructure requires funding formaintenance and growth. The size and complexity of the infrastructurecan make it difficult to forecast and track funding requirements.Effective scheduling information for funding is needed.

In another example, the storage infrastructure is typically underconstant change as new systems are planned, tested, and operated. Thesize and complexity of the infrastructure can make it difficult to trackthe current status of applications and systems. Information on thestatus of applications and systems is needed.

SUMMARY OF THE INVENTION

Examples of the invention include data storage infrastructures andmethods for a communication network that produces a plurality of dataflows of network data. The data storage infrastructure comprises aplurality of data storage systems and a storage management system. Thedata storage systems are configured to store the network data. Thestorage management system is configured to identify characteristics forthe data flows, score the characteristics for the data flows, andprocess the scores to assign individual ones of the data flows toindividual ones of the data storage systems.

In some examples of the invention, the different ones of the datastorage systems have different data storage reliabilities.

In some examples of the invention, the storage management system isconfigured to normalize the scores.

In some examples of the invention, the storage management system isconfigured to sum the scores for the individual data flows.

In some examples of the invention, the characteristics indicate users ofthe data flows.

In some examples of the invention, the characteristics indicate monetaryvalues of the data flows.

In some examples of the invention, the characteristics indicatepriorities of the data flows.

In some examples of the invention, the characteristics indicatelife-cycles of the data flows.

In some examples of the invention, the characteristics indicate legalcompliance requirements of the data flows.

In some examples of the invention, the characteristics indicateperformance requirements of the data flows.

BRIEF DESCRIPTION OF THE DRAWINGS

The same reference number represents the same element on all drawings.

FIG. 1 illustrates a communication system having a storageinfrastructure in an example of the invention.

FIG. 2 illustrates a storage management system in an example of theinvention.

FIG. 3 illustrates a process for assigning data flows to storage systemtiers in an example of the invention.

FIG. 4 illustrates a GUI for assigning data flows to data classes in anexample of the invention.

FIG. 5 illustrates a GUI for assigning data flows to information classesin an example of the invention.

FIG. 6 illustrates a GUI for assigning variables to data flows in anexample of the invention.

FIG. 7 illustrates a GUI for assessing personnel gaps in an example ofthe invention.

FIG. 8 illustrates a GUI for assessing process gaps in an example of theinvention.

FIG. 9 illustrates a GUI for assessing technology gaps in an example ofthe invention.

FIG. 10 illustrates a GUI for providing a cost model in an example ofthe invention.

FIG. 11 illustrates a GUI for providing a cost model in an example ofthe invention.

FIG. 12 illustrates a GUI for providing a cost model in an example ofthe invention.

FIG. 13 illustrates a GUI for providing a cost model in an example ofthe invention.

FIG. 14 illustrates a GUI for providing an employee model in an exampleof the invention.

FIG. 15 illustrates a GUI for providing an employee model in an exampleof the invention.

FIG. 16 illustrates a GUI for providing an inventory model in an exampleof the invention.

FIG. 17 illustrates a GUI for providing product information for thestorage infrastructure in an example of the invention.

FIG. 18 illustrates a GUI for providing product information for thestorage infrastructure in an example of the invention.

FIG. 19 illustrates a GUI for providing product information for thestorage infrastructure in an example of the invention.

FIG. 20 illustrates a GUI for providing funding information for thestorage infrastructure in an example of the invention.

FIG. 21 illustrates a GUI for providing funding information for thestorage infrastructure in an example of the invention.

FIG. 22 illustrates a GUI for providing funding information for thestorage infrastructure in an example of the invention.

FIG. 23 illustrates a GUI for providing application assignmentinformation in an example of the invention.

FIG. 24 illustrates a GUI for providing status and implementationinformation for applications and systems in an example of the invention.

FIG. 25 illustrates a GUI for providing status and implementationinformation for applications and systems in an example of the invention.

FIG. 26 illustrates a GUI for providing status and implementationinformation for applications and systems in an example of the invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

FIGS. 1-26 and the following description depict specific examples toteach those skilled in the art how to make and use the best mode of theinvention. For the purpose of teaching inventive principles, someconventional aspects have been simplified or omitted. Those skilled inthe art will appreciate variations from these examples that fall withinthe scope of the invention. Those skilled in the art will appreciatethat the features described below can be combined in various ways toform multiple variations of the invention. As a result, the invention isnot limited to the specific examples described below, but only by theclaims and their equivalents.

Data Storage for a Communication Network

FIG. 1 illustrates communication network 100 in an example of theinvention. Communication network 100 includes communication networkelements 101, back-office systems 102, storage interfaces 103, storagesystems 111-113, and storage management system 114. Storageinfrastructure 110 is a part of communication network 100 that comprisesstorage interfaces 103, storage systems 111-113, and storage managementsystem 114. Storage systems 111-113 are separated into tiers 1-N, wheresystem 111 provides tier 1 storage, system 112 provides tier 2 storage,and system 113 provides tier N storage. As indicated on FIG. 1, therecould be many storage tiers.

Communication network elements 101 exchange user communications 104between network users to provide communication services. Thecommunication services could include wireless, interne, telephony,video, data, or some other communications service. The network usersmaybe customers of communication network 100 or they may be othercommunication networks (having their own customers). Communicationnetwork elements 101 could include telephony switches, packet routers,wireless base stations, servers, databases, call processors,communication gateways, optical systems, and other communicationequipment that are required to support the communication servicesprovided by communication network elements 101. Communication networkelements 101 transfer element data 105 to back-office systems 102.Element data 105 includes billing information, performance information,user content, and other data that is generated or handled bycommunication network elements 101.

Back-office systems 102 receive element data 105 from communicationnetwork elements 101. Back-office systems 102 also receive other data106 from other network systems and personnel (not shown). Back-officesystems 102 comprise servers and computer systems that are configured tobe network element management systems, customer information systems,order entry systems, communication probes, and other systems thatsupport the communication services provided by communication networkelements 101.

For example, network elements 101 can include Service Control Points(SCPs) and back office systems 102 can include an SCP management system.Network elements 101 can include local telephone switches and backoffice systems 102 could include a telephony billing system. Networkelements 101 can include a packet network and back office systems 102could include a picture mail server. Network elements 101 and backoffice systems 102 could include numerous other systems.

Back-office systems 102 process element data 105 and other data 106 totransfer network data 107 to storage interfaces 103. Storage interfaces103 could be Storage Area Network (SAN) switches, Network-AttachedStorage (NAS) gateways, and other devices that exchange data betweenback-office systems 102 and storage systems 111-113. Storage interfaces103 transfer network data 107 to storage systems 111-113. Thus, storageinterfaces 103 direct network data 107 to the appropriate ones ofstorage systems 111-113.

Storage systems 111-113 receive and store network data 107. Storagesystems 111-113 could include disk memory systems, tape memory systems,integrated circuitry memory systems, or some other type of data storagesystem or media. Note that storage systems 111-113 are tiered based onperformance, where tier 1 has the best performance and tier N has thepoorest performance. Typically, tier 1 is the most expensive and tier Nis the least expensive. Performance can be measured based onavailability. For example, tier 1 storage system 111 may have 99.999% orhigher availability and exceptional performance, and tier N storagesystem 113 may have 97%-99.0% availability. Mid-range tiers could haveavailabilities in between 99.0% and 99.999%. For example, tier 2 storagesystem 112 could have 99.9% to 99.999% availability. Other performancemeasures, such as retrieval speeds or disaster recovery features, couldalso factor into assigning a tier value to storage systems 111-113.

Storage management system 114 is coupled to back-office systems 102,storage interfaces 103, and storage systems 111-113 by control links115. Storage management system 114 manages several aspects of storageinfrastructure 110 and is described in detail below.

FIG. 2 illustrates storage management system 114 in an example of theinvention. Storage management system 114 includes communicationinterface 201, processing system 202, and user interface 203. Processingsystem 202 includes storage system 204. Storage system 204 storessoftware 205. Processing system 202 is linked to communication interface201 and user interface 203. Storage management system 114 could becomprised of a programmed general-purpose computer, although thoseskilled in the art will appreciate that programmable or special purposecircuitry and equipment may be used. Storage management system 114 mayuse a client server architecture where operations are distributed amonga server system and client devices that together comprise elements201-205.

Communication interface 201 is coupled to control link 115.Communication interface 201 could comprise a network interface card,modem, port, or some other communication device. Communication interface201 may be distributed among multiple communication devices. Processingsystem 202 could comprise a computer microprocessor, logic circuit, orsome other processing device. Processing system 202 may be distributedamong multiple processing devices. User interface 203 includes aGraphical User Interface (GUI) display and could also comprise akeyboard, mouse, voice recognition interface, microphone and speakers,or some other type of user device. User interface 203 may be distributedamong multiple user devices. Storage system 204 could comprise a disk,tape, Write Once Read Many (WORM) device, storage appliance, integratedcircuit, server, or some other memory device. Storage system 204 may bedistributed among multiple memory devices.

Processing system 202 retrieves and executes software 205 from storagesystem 204. Software 205 may comprise an operating system, utilities,drivers, networking software, and other software typically loaded onto ageneral-purpose computer. Software 205 could comprise an applicationprogram, firmware, or some other form of machine-readable processinginstructions. When executed by processing system 202, software 205directs processing system 202 to operate as described herein.

Note that storage management system 114 may be concentrated in a singlesystem or distributed across many systems. In some examples, storagemanagement system 114 uses a client server architecture having a centralserver (i.e. processing system 202) and multiple client devices (i.e.user interfaces 203) so multiple users may simultaneously use storagemanagement system 114.

Data Flow Assignment to Storage System Tiers

FIG. 3 illustrates the operation of storage management system 114 whenassigning an application data flow to a storage system tier in anexample of the invention. The reference numbers from FIG. 3 areindicated parenthetically below. Typically, the tier assignment isaccomplished by an operator interacting with storage management system114 through its GUI. To determine the tier assignment, the data flow isfirst analyzed to determine various factors for the data flow.

Storage management system 114 starts the process by identifying anapplication and by identifying the data flows for the application (301).Typically, communication network personnel will identify applicationsand their data flows to the operator for entry into storage managementsystem 114. An application is any functionality in communication network100 that provides network data 107. The network data 107 for theapplication can be separated into identifiable data flows. A singleapplication can have one data flow or multiple data flows. For example,the application could be a push-to-talk service that has individual dataflows for billing, customer information, and performance information.

For a given data flow, storage management system 114 classifies the datain the data flow (302). The data classes include:

Communication Path—data that is associated with the set-up and operationof communication sessions for customers. For example, the routing datastored in an SCP would be classified in the communication path dataclass.

Accounting—data that indicates network utilization so the users may becharged for communication services. For example, call detail records forindividual calls would be classified in the accounting data class.

Fault and Alarm—data that indicates problems with communication networkelements 101. For example, a Synchronous Optical Network (SONET) alarmindicating an optical fiber cut would be classified in the fault andalarm data class.

Configuration—data that is associated with the addition, deletion, andmodification of the connections and topology of communication network100. For example, a network architecture data flow would be classifiedin the configuration data class.

Performance—data that indicates network performance measurements. Forexample, a data flow from a probe that measures the number of packetstransferred over a connection would be classified in the performancedata class.

Security—data that controls access to network resources and sensitivedata. For example, authorization codes that allow operations personnelto access and program Internet routers would be classified in thesecurity data class.

Content—data that includes content that is received from or delivered tocustomers. For example, videos that are available for customer downloadwould be classified in the customer content data class.

Legal Compliance—data that is required by applicable laws orregulations. For example, data required for compliance withSarbanes-Oxley regulations would be classified in the legal compliancedata class.

Statistical Analysis—data that indicates network analysis and reports.For example, data for reporting network outages to government agencieswould be classified in the statistical analysis data class.

Service Level Agreement (SLA) Management—data class that indicatescompliance with customer service agreements. For example, troubletickets that impact a customer's service would be classified in the SLAmanagement data class.

To classify the data in the data flow, storage management system 114provides the operator with a choice of data classes for each data flowthrough a drop down menu or some other GM mechanism. All data flows areclassified into a consistent set of data classes. For example, FIG. 4shows GUI 400 with table 401 for identifying applications, data flows,and data classes through operator entry. The data classes forapplication “A” have already been selected. After the operator positionsthe GUI cursor (indicated by an “X” on FIG. 4) over the field forentering the data class for data flow #1 of application “B”, drop downmenu 402 appears with the data classes for selection. The operator maythen position the cursor over the selected data class for automaticentry of the selected data class into the field.

For a classified data flow, storage management system 114 identifies afunctionality for the data flow (303). The functionality represents thepurpose of the data flow. To identify a functionality for the data flow,the operator is given a choice of functions through a drop down menu orsome other GUI mechanism. All data flows are attributed withfunctionality from a consistent set of functions. Although there aretypically numerous functions, a small example of functions could be:

Function #1—Phone activation.

Function #2—Data link provisioning.

Function #3—Customer billing.

Function #4—Optical network alarms.

Function #5—Sarbanes-Oxley reporting.

Like the GUI operations depicted above, the operator may position theGUI cursor over the function field for a given data flow, and a dropdown menu box appears with the functions for selection. The operator mayposition the cursor over the selected function range for automatic entryof the selected function into the field.

For a given data flow, storage management system 114 identifies a userfor the data flow (304). The user represents the entity in communicationnetwork 100 that needs the data storage for the data flow. To identify auser for the data flow, the operator is given a choice of users througha drop down menu or some other GUI mechanism. All data flows areattributed with users from a consistent set of users. Although there aretypically numerous users, a small example of users could be:

User #1—Wireless network operations.

User #2—Customer service.

User #3—Packet network design.

User #4—Optical network procurement.

User #5—Legal.

Like the GUI operations depicted above, the operator may position theGUI cursor over the user field for a given data flow, and a drop downmenu box appears with the users for selection. The operator may positionthe cursor over the selected user for automatic entry of the selecteduser into the field.

For a given data flow, storage management system 114 attributes a valueto the data flow (305). The value represents a monetary value of thedata flow to communications network 100. To attribute a value to thedata flow, the operator is given a choice of monetary ranges for eachdata flow through a drop down menu or some other GUI mechanism. All dataflows are attributed with a value from a consistent set of monetaryranges. For example, monetary ranges could be:

Range #1—less than $1,000,000.

Range #2—$1,000,000 to $10,000,000.

Range #3—$10,000,001 to $100,000,000.

Range #4—$100,000,001 to $1,000,000,000.

Range #5—Over $1,000,000,000.

Like the GUI operations depicted above, the operator may position theGUI cursor over the value field for a given data flow, and a drop downmenu box appears with the monetary ranges for selection. The operatormay position the cursor over the selected monetary range for automaticentry of the selected range into the field.

Storage management system 114 attributes a priority to the data flow(306). The priority represents the importance of the data flow tocommunication network 100 in terms of access delay, geographicallydiverse back-up, and disaster recovery. To attribute a priority to thedata flow, the operator is given a choice of priority levels for eachdata flow through a drop down menu or some other GUI mechanism. All dataflows are attributed with a priority from a consistent set of prioritylevels. For example, priority levels could be:

Priority Level #1—data access in less than 10 seconds with geographicdiversity and disaster recovery.

Priority Level #2—data access in less than 1 hour with geographicdiversity and disaster recovery.

Priority Level #3—data access in less than 1 day with geographicdiversity and disaster recovery.

Priority Level #4—data access in less than 1 day with geographicdiversity and without disaster recovery.

Priority Level #5—data access in less than 1 day without geographicdiversity and without disaster recovery.

Like the GUI operations depicted above, the operator may position theGUI cursor over the priority field for a given data flow, and a dropdown menu box appears with the priority levels for selection. Theoperator may position the cursor over the selected priority level forautomatic entry of the selected level into the field.

Storage management system 114 attributes a life-cycle to the data flow(307). The life-cycle represents a time period during which the dataflow retains value to communications network 100. To attribute alife-cycle to the data flow, the operator is given a choice of timeperiods for each data flow through a drop down menu or some other GUImechanism. All data flows are attributed with a life-cycle from aconsistent set of time periods. For example, time periods could be:

Life-cycle #1—less than 7 days.

Life-cycle #2—8 days to 31 days.

Life-cycle #3—32 days to one year.

Life-cycle #4—one year to five years.

Life-cycle #5—greater than five years.

Like the GUI operations depicted above, the operator may position theGUI cursor over the life-cycle field for a given data flow, and a dropdown menu box appears with the time periods for selection. The operatormay position the cursor over the selected time period for automaticentry of the selected period into the field.

Storage management system 114 attributes compliance requirements to thedata flow (308). The compliance requirements indicate if the data flowneeds to be kept for legal purposes. To attribute compliancerequirements to the data flow, the operator is given a choice ofcompliance types for each data flow through a drop down menu or someother GUI mechanism. All data flows are attributed with compliancerequirements from a consistent set of compliance types. For example,compliance types could be:

Compliance Type #1—required by the Federal Communication Commission(FCC).

Compliance Type #2—required by Sarbanes-Oxley.

Compliance Type #3—required by the Internal Revenue Service (IRS).

Compliance Type #4—none.

Like the GUI operations depicted above, the operator may position theGUI cursor over the compliance field for a given data flow, and a dropdown menu box appears with the compliance types for selection. Theoperator may position the cursor over the selected compliance type forautomatic entry of the compliance requirements into the field.

Storage management system 114 attributes inter-dependencies to the dataflow (309). The inter-dependencies indicate other applications that aredependent on the current data flow. To attribute inter-dependencies tothe data flow, the operator is given a choice of other applications foreach data flow through a drop down menu or some other GUI mechanism. Alldata flows are attributed with inter-dependencies from a consistent setof applications.

Like the GUI operations depicted above, the operator may position theGUI cursor over the inter-dependencies field for a given data flow, anda drop down menu box appears with the applications for selection. Theoperator may position the cursor over the selected application forautomatic entry of the selected applications into the field.

Storage management system 114 attributes performance requirements to thedata flow (310). The performance requirements indicate any specificindustry-recognized performance metrics that are required for the dataflow. To attribute performance requirements to the data flow, theoperator is given a choice of industry-recognized performance metricsfor each data flow through a drop down menu or some other GUI mechanism.All data flows are attributed with performance requirements from aconsistent set of performance metrics.

Like the GUI operations depicted above, the operator may position theGUI cursor over the performance requirements field for a given dataflow, and a drop down menu box appears with the performance metrics forselection. The operator may position the cursor over the selectedperformance metric for automatic entry of the selected requirements intothe field.

The data flow may also be associated with other factors in a similarmanner. In addition, some of the factors described above could beomitted.

For a given data flow, storage management system 114 classifies theinformation represented by the data (311). The information classesinclude:

Service path—information related to service set-up and operation. Forexample, a data flow having routing information stored in an SCP wouldbe classified in the service path information class.

Revenue—information related to revenue generation and support. Forexample, a data flow of call detail records would be classified in therevenue information.

Operational Support—information related to faults, alarms, and thestatus of communication network elements 101. For example, a SONET alarmindicating an optical fiber cut would be classified in the operationalsupport information class.

Content—information related to the content that is received from ordelivered to customers. For example, videos that are available forcustomer download would be classified in the content information class.

Compliance and Reporting—information that is required by applicable lawsor regulations. For example, information required for compliance withSarbanes-Oxley regulations would be classified in the compliance andreporting data class.

To classify the information in the data flow, storage management system114 provides the operator with a choice of information classes for eachdata flow through a drop down menu or some other GUI mechanism. All dataflows are classified into a consistent set of information classes. Forexample, FIG. 5 shows GUI 500 with table 501 for identifyingapplications, data flows, and information classes through operatorentry. The information classes for application “A” have already beenselected. After the operator positions the GUI cursor (indicated by an“X” on FIG. 5) over the field for the information class for data flow #1of application “B”, drop down menu 502 appears with the informationclasses for selection. The operator may position the cursor over theselected information class for automatic entry of the selected classinto the field.

The above factors are data class, functionality, user, value, priority,life-cycle, compliance, inter-dependencies, performance, and informationclass. As noted, the factors that network management system 114 makesavailable for selection are controlled and consistent. Each factor thatis available for selection has a corresponding score. For example, thelife-cycle factors could be scored as follows:

Life-cycle #1—less than 7 days: score=1.

Life-cycle #2—8 days to 31 days: score=2.

Life-cycle #3—32 days to one year: score=3.

Life-cycle #4—one year to five years: score=4.

Life-cycle #5—greater than five years: score=5.

For a given data flow, the scores for all of its factors are addedtogether to get a total score for the data flow (312). Prior to summingto the total score, the individual scores may be normalized. Forexample, the life-cycle scores could be normalized by dividing by 5, sothat all life-cycle scores are between zero and one. Prior to summingthe total score, the individual scores may be weighted to emphasize orde-emphasize a given factor. For example, life-cycle scores could bemultiplied by 1.5 to increase the importance of the life-cycle factorrelative to the other factors, but priority scores could be multipliedby 0.5 to decrease the importance of the priority factor relative to theother factors. Once the individual scores are normalized and weighted,the normalized and weighted individual scores are summed to obtain thetotal score for the data flow.

For the data flow, a set of key variables is assessed to determinecompatibility between the data flow and the various classes of service(313). In this example the classes of service are: extremely critical,mission critical, business critical, and back-office/reporting, althoughdifferent classes-of-service could be used. The key variables are:

Access Frequency—what is the amount of access to the data that will beneeded during a given time period.

Archival and Deletion—does the data need to be stored for more than agiven time period and does the data need to be deleted at a given timein the future.

Availability—what percent of time must the storage system be able toprovide the data.

Back-up—does the data need to be stored in the system at all.

Business Continuity and Disaster Recovery—what level of businesscontinuity and/or disaster recovery capability is required. For example,is protection required from a simultaneous two-site failure.

Communication Path—is the data required for the establishment andoperation of communication paths for customers.

Primary Repository—will the storage system be the primary source of thedata

Connectivity—what type of Input/Output (I/O) is required for dataaccess.

Data Loss—what percent of the data can be lost.

Data Migration—what percent of the data must be ported to other systems

Data Change—what percent of the data changes over a given time period.

Policy Enforcement—are there polices regarding the ability to change ordelete the data.

Disk-based Replication—is disk-based back-up required for the data.

Geographic Locations—how many storage sites are required for the data.

Business Impact—is there a significant business impact if the data islost.

Load Balancing and Multi-Pathing—are load balancing and/or multipathingneeded to support I/O requirements for the data.

Monitoring Requirements—what are the requirements for checking andreporting the status of the storage system.

Operational Flexibility—how flexible must the storage system be tohandle changes in I/O, capacity, or other items.

Performance—are there any specific performance requirements for thedata.

Provisioning—how fast does the storage service need to be establishedfor the data

Recovery Techniques—what recovery techniques are needed. For example, ispoint-in-time recovery needed.

Recovery Timeframe—what is the allowed time period for data recovery.

Response Time—what is the allowed time period to provide the data toexternal systems.

Service Loss—how much service loss is acceptable during data recovery.

For each class of service, the variables values are:

Back- Extremely Mission Business office, Variable Critical CriticalCritical Reporting Access Very High Very High High Medium frequencyArchival and Yes Yes Yes Yes deletion Availability 99.999% 99.990% to99.90% to 97.0% to 99.90% 99.0% 99.0% Back-up Yes Yes Yes Yes BusinessYes Yes No No continuity and disaster recovery Com. path Yes No No NoCompliance No No No Yes Connectivity Multiple Multiple Multiple SLAspecific Data loss No Recoverable Recoverable Appli- up to a point up toa point cation in time in time specific Data Yes Yes Yes Yes migrationData change Very high Very high Very high High Policy Yes Yes Yes Yesenforcement Disk-based Yes Yes, for No No replication selected dataGeographic Multiple Multiple for No No locations selected data BusinessYes Yes No No impact Load bal- Yes Yes Yes SLA ancing and specificmultipathing Monitoring 27 × 7 × 365 27 × 7 × 365 27 × 7 × 365 Periodicrequirements immediate immediate immediate alert alert alert alertduring business hours Operational High High High High flexibilityPerformance Exceptional Exceptional High Medium Provisioning 1-3 days1-3 days 1-5 days 5-7 days Recovery Point-in-time, Point-in-time,Point-in- Point-in- techniques Multiple geo- Multiple geo- time timegraphical sites, graphical sites, synchronous & synchronous &asynchronous asynchronous Recovery 10-59 minutes 1-12 hours 12-48 hours2-5 busi- timeframe ness days Response Very high Very high High Hightime Service loss No Brief Yes Yes

To assess the key variables for the data flow, storage management system114 provides the operator with a choice of variable values for the dataflow through a drop down menu or some other GUI mechanism. All dataflows use a consistent set of variables and values. For example, FIG. 6shows GUI 600 with table 601 for identifying applications, data flows,and variable values through operator entry. For application “A” —dataflow #1, the values for access frequency and archival & deletion arerespectively “HIGH” and “YES.” After the operator positions the GUIcursor (indicated by an “X” on FIG. 6) over the field for“AVAILABILITY,” drop down menu 602 appears with the availability valuesfor selection. The operator may position the cursor over the selectedvalue for automatic entry of the selected availability value into thefield.

Storage management system 114 selects the class of service for the dataflow based on the key variables and the total score (314). For example,once the variables are selected for the data flow, storage managementsystem 114 compares the data flow variables against the class-of-servicevariables to determine which classes-of-service are suitable for thedata flow. The total score is used to select from among the suitableclasses of service. For example, both the extremely critical and missioncritical classes-of-service may be suitable for a given data flow. Theextremely critical class-of-service may be used if the data flow has atotal score higher than 10 and the mission critical class-of-service maybe used if the data flow has a total score of 10 or lower.

For the data flow, storage management system 114 selects a storagesystem tier based on the selected class of service (315). Typically,each class-of-service is pre-assigned to a storage system tier. Newtiers and classes-of-service may be implemented over time.

In some examples, storage management system 114 may transfer controlmessages indicating the selected storage system tier for the data flowto the selected tier of storage systems 111-113 and to storageinterfaces 103. In response to the control messages, storage interfaces103 route the data flow to the selected tier, and the storage system inthe selected tier stores the data and provides the various storagefeatures available at that tier.

It should be appreciate that storage management system 114 provides atool for assisting the operator in assigning data flows to storagetiers. Advantageously, storage management system 114 requires theoperator to consider a rigorous set of factors and variables in aconsistent and disciplined manner for each data flow. The result is ahigh-quality and consistent approach to the assignment of data flows todata storage system tiers.

Technology and Personnel Management

Network management system 114 manages storage infrastructure personnel,processes, technology in some examples of the invention. To accomplishthis task, network management system 114 interacts with an operatorthrough its GUI to develop a current and future view of the personnel,processes, and technology for storage infrastructure 110.Advantageously, network management system 114 requires the operator toapply a rigorous and detailed analysis to accurately identify the gapsbetween the current state and a desired future state for storageinfrastructure 110 at the personnel, process, and technology levels.

FIG. 7 illustrates GUI 700 that is provided by network management system114 to manage personnel. The left column of GUI 700 lists variousservices that are provided by storage infrastructure personnel. Theseservices comprise:

Architecture Design—technical planning for the storage system.

Asset Management—care of the storage system equipment.

Back-up—assessing whether data should be stored in the storage system.

Billing—charging and receiving money from storage system users.

Capacity Management—planning and control of storage system capacity.

Change Management—planning and control over changes to the storagesystem.

Configuration Management—planning and control over storage systemequipment configurations.

Data Movement—planning and control over data migration and transfer.

Customer Relationship—interface with storage system users.

Disaster Recovery—planning and control over storage systemequipment/site failure.

Life-cycle management—planning and control over storage and deletiontime frames.

Problem Management—Trouble-shooting and remediation.

Monitoring—assessing storage system status and notifying systempersonnel and users of issues.

Performance Management—measuring storage system performance againstSLAs.

Procurement—acquiring and installing storage system equipment.

Provisioning—establishing storage services for new applications.

Replication—copying data to a back-up storage systems.

Reporting—generating technical information about the storage system.

Restoration—recovering data after storage system failure.

The top row of GUI 700 includes several categories to prompt operatorinput or indicate management system output. The categories are:

Currently Delivered—indicates that personnel provide the service atpresent.

Primary Organization—indicates the main organization that provides theservice.

Current Hours—indicates the number of hours that the primaryorganization spends providing the service per time period (hours permonth for example).

Targeted Hours—indicates a desired number of hours that the primaryorganization should spend providing the service in a future time period.(hours in the next month for example).

Secondary Organization—indicates any support organization that helpsprovide the service.

Current Hours—indicates the number of hours that the secondaryorganization spends providing the service per time period (hours permonth for example).

Targeted Hours—indicates a desired number of hours that the secondaryorganization should spend providing the service in a future time period.(hours in the next month for example).

Personnel Gap—indicates the difference between the current hours and thetargeted hours for the primary and secondary organizations.

For each service, storage management system 114 obtains a yes or noresponse from the operator in the Currently Delivered column on GUI 700.For any services that are currently being delivered, storage managementsystem 114 uses GUI 700 to obtain the primary organization thatcurrently provides the service from the operator. GUI 700 also obtainsany secondary organizations that currently provide the service. Like theGUI operations depicted above, the operator may position the GUI cursorover the primary organization field or secondary organization field fora given service, and a drop down menu box appears with the variousorganizations for selection. The operator may position the cursor overthe selected organization for automatic entry of the selectedorganization into the field.

For any services that are currently being delivered, storage managementsystem 114 uses GUI 700 to obtain the current hours that the primaryorganization and any secondary organizations use to provide the service.For each service, storage management system 114 uses GUI 700 to obtainthe targeted hours that the primary organization and any secondaryorganizations should use to provide the service.

On a per-service basis, network management system 114 totals the currenthours for the primary and secondary organizations and totals thetargeted hours for the primary and secondary organizations. On aper-service basis, network management system 114 subtracts the total oftargeted hours from the total for current hours to identify thepersonnel gap for that service. Network management system 114automatically indicates the personnel gaps on a per-service basis in theright column of GUI 700.

For all services, network management system 114 totals the current hoursfor the primary and secondary organizations and totals the targetedhours for the primary and secondary organizations. Network managementsystem 114 subtracts the total of targeted hours (for all services) fromthe total for current hours (for all services) to identify the personnelgap for all services. Network management system 114 automaticallyindicates the personnel gap for all services at the right in the bottomrow of GUI 700.

FIG. 8 illustrates GUI 800 that is provided by network management system114 to manage process. The left column of GUI 800 lists various servicethat are provided by storage infrastructure personnel and describedabove for FIG. 7. The top row of GUI 800 includes several categories toprompt operator input or indicate management system output. Thecategories are:

Documented Process Exists—indicates if the service follows a documentedprocess, such as a pert chart.

Primary Process Owner—indicates the main organization that provides theservice.

Secondary Process Owner—indicates any support organization that helpsprovide the service.

Primary Process User—indicates the main organization that uses theservice.

Secondary Process User—indicates any other organizations that useservice.

Current Maturity Level—indicates the current complexity of the process.

Targeted Maturity Level—indicates the desired complexity of the service.

Process Gaps—indicates the difference between the current maturity leveland the targeted maturity level for each service.

For each service, storage management system 114 obtains a yes or noresponse from the operator in the Documented Process column on GUI 800.For each service, storage management system 114 uses GUI 800 to obtainthe primary organization that currently provides the service from theoperator. GUI 800 obtains any secondary organizations that currentlyprovide the service. Likewise, GUI 800 also obtains primary andsecondary process users from the operator. Like the GUI operationsdepicted above, the operator may position the GUI cursor over a processowner or user field for a given service, and a drop down menu boxappears with the various organizations for selection. The operator mayposition the cursor over the selected organization for automatic entryof the selected organization into the field.

For each service, storage management system 114 uses GUI 800 to obtainthe current maturity level of the process and the desired maturity levelfor the process. Like the GUI operations depicted above, the operatormay position the GUI cursor over a maturity level field for a givenservice, and a drop down menu box appears with the various maturitylevels for selection. The operator may position the cursor over theselected level for automatic entry of the selected maturity level intothe field.

For example, a maturity index could be defined from one to ten where anindex of one indicates minimum complexity and an index of ten indicatesmaximum complexity. The various indexes could be differentiated byreference to industry standards, technologies, or other applicabledescriptions. Thus, a maturity index could be used to indicate thecurrent maturity level of the process for the service.

On a per-service basis, network management system 114 compares thecurrent and targeted maturity levels to determine the difference. If amaturity index is used, the numerical difference between the two indexescould be used. Network management system 114 automatically indicates thematurity difference on a per-service basis in the right column of GUI800.

FIG. 9 illustrates GUI 900 that is provided by network management system114 to manage technology. The left column of GUI 900 lists variousservices that are provided by storage infrastructure personnel anddescribed above for FIG. 7. The top row of GUI 900 includes severalcategories to prompt operator input or indicate management systemoutput. The categories are:

Existing Hardware & Vendor—indicates the current equipment used toprovide the service and the supplier of the equipment.

Existing Software & Vendor—indicates the current software used toprovide the service and the supplier of the software.

Existing External Services—indicates external resources (contractors andservice providers for example) that are used to provide the service

Gaps—indicates the personnel and process gaps from GUIs 700 and 800.

Hardware to be purchased—indicates additional hardware to be purchasedand installed.

Software to be purchased—indicates additional software to be purchasedand installed.

External Service to be purchased—indicates additional external resourcesto be purchased.

For each service, storage management system 114 obtains the existinghardware, software, and external services from the operator in theapplicable columns on GUI 900. For each service, storage managementsystem 114 indicates the personnel and process gaps developed in GUI 700and GUI 800. Like the GUI operations depicted above, the operator mayposition the GUI cursor over a given field, and a drop down menu boxappears with the various items for selection. The operator may positionthe cursor over the selection for automatic entry of the selection intothe field.

For each service, storage management system 114 uses GUI 900 to obtainfrom the operator the hardware, software, and external services to bepurchased and to obtain the time of the purchase. When making apurchasing decision for a service, the operator can view the existingtechnology (hardware, software, external services) used to deliver theservice, and the operator can also view the personnel and process gapsfor the service. Advantageously, network management system 114 enablespurchasing decisions to be made that close these gaps. Thus, technologyis used to reduce personnel gaps and to improve process maturity.

Storage Infrastructure Cost Model

Storage infrastructure 110 includes numerous storage systems 111-113that include disks, tape, and other memory devices and media. Storageinfrastructure 110 includes numerous computer systems, such as servers,that form a part of storage interfaces 103 and provide I/O to thestorage systems 111-113. Sometimes, these computer systems have internalstorage devices, such as internal disks, that also form a part ofstorage systems 111-113. In addition, storage infrastructure 110requires personnel, communication networking, operating environments,and other numerous other resources.

Network management system 114 manages costs associated with storageinfrastructure 110 in some examples of the invention. To accomplish thistask, network management system 114 interacts with an operator throughits GUI to develop individual cost models for the individual computersystems and storage systems that comprise storage infrastructure 110.For each computer system and storage system, network management system114 processes the model to provide a cost per unit of storage, such asdollars per Gigabit (GB). Advantageously, network management system 114allows for direct comparison of the costs associated with the variouscomputer systems and storage systems to improve the management ofstorage infrastructure 110.

FIGS. 10-13 illustrate GUI 1000 that is provided by network managementsystem 114 to manage cost. The left column of GUI 1000 lists variouscost parameters related to employees, servers, internal disks, externaldisks, tape, networking, software, additional equipment, environment,outages, growth, and finance. The top row lists various computer systemsand storage systems. The number of computer and storage systems could bemuch larger and has been restricted for clarity.

In some cases, the operator may directly enter data for a givenparameter of a given system. In other cases, the operator may positionthe GUI cursor over a data field, and a drop down menu box appears withthe various values for selection. The operator may position the cursorover the selected value for automatic entry of the selected value intothe data field. In yet other cases, network management system 114 mayretrieve the value from another system or calculate the value from otherinputs. Thus, GUI 1000 is filled with information on a per computersystem or per storage system basis. Network management system 114 thenprocesses that information to provide comparative costs and comments forthe computer and storage systems.

The cost parameters for employee costs are:

Number of primary Full Time Employees (FTEs)—the number of FTEs whoseprimary task is associated with a given storage or computer system.

Annual cost per primary FTEs—an estimate of the annual burdened cost ofa primary FTE.

Number of secondary FTEs—the number of FTEs whose primary task is notassociated with a given storage or computer system, but who aresecondarily associated with a given storage or computer system.

Annual cost per secondary FTEs—an estimate of the annual burdened costof a secondary FTE.

Additional FTE costs—extra costs for FTEs not captured above, such astraining and retention costs.

Service contract costs—annual costs for personnel service contracts.

% of storage cost for FTEs—FTE costs divided by total costs.

The parameters for computer system (server) costs are:

Number of servers—the total number of servers.

Average cost of small servers—the cost of servers with 1 CentralProcessing Unit (CPU).

Average cost of medium servers—the cost of servers with 2-3 CPUs.

Average cost of large servers—the cost of servers with 4 or more CPUs.

% of infrastructure comprised of small servers—the ratio of smallservers to all servers as indicated by relative number of CPUs,transactions per second, number of servers, or some other metric.

% of infrastructure comprised of medium servers—the ratio of mediumservers to all servers as indicated by relative number of CPUs,transactions per second, number of servers, or some other metric.

% of infrastructure comprised of large servers—the ratio of largeservers to all servers as indicated by relative number of CPUs,transactions per second, number of servers, or some other metric.

Servers saved by consolidation—an estimate of the number of servers thatwould be saved by using large servers.

Number of years for server amortization—the number used by accountingfor tax purposes.

% of server costs not for internal disks—the ratio of server costs thatare not internal disk costs, such as software and accessory costs, tothe total server costs.

% of server cost for environment—environmental costs divided by totalcosts.

The cost parameters for internal disk costs are:

Total cost of internal disks—the total cost for all internal disks.

Total data capacity of internal disks—the total data capacity of allinternal disks.

Available data capacity of internal disks—the unused but available datacapacity of all internal disks.

Purchased but uninstalled capacity—the data capacity for internal disksthat are paid for but not yet available in the storage system.

% of storage cost for internal disks—internal disk costs divided bytotal costs.

The cost parameters for external disk costs are:

Total data capacity of external disks—the total data capacity of allexternal disks.

Available data capacity of external disks—the unused but available datacapacity of all external disks.

Purchased but uninstalled capacity—the data capacity for external disksthat are paid for but not yet installed.

Number of years for external disk amortization—the number used byaccounting for tax purposes.

Annual disk configuration fees—the annual cost of configuring externaldisks.

Annual disk maintenance fees—the annual cost of maintaining externaldisks.

Annual cost per GB for external disks—total cost for external disksdivided by the total storage capacity of the external disks.

% of storage cost for external disks—external disk costs divided bytotal costs.

The cost parameters for tape costs are:

% of tape capacity in use—the amount of data on tape divided by thetotal storage capacity of tape.

Number of tape drives—the total number of tape drives.

Number of tape libraries—the total number of multiple tape drive systems(tape libraries).

Average capacity of tape cartridges—the storage capacity of a tapecartridge.

Number of tape cartridges—the number of tape cartridges.

Annual tape hardware cost—the total yearly cost for tape hardware.

Annual tape vaulting cost—the total yearly cost for tape vaulting.

Annual tape media cost—the total yearly cost for the tape itself.

Number of years for tape system amortization—the number used byaccounting for tax purposes.

% of storage cost for tape—tape costs divided by total costs.

The cost parameters for networking costs are:

Total network costs—the cost of the communication network serving thestorage network

% of network used for storage—the amount of bandwidth used by the givensystem divided by the total bandwidth of the communication network.

Amount of data backed-up per day—the daily GB of data transferred overthe network to/from a given system for back-up.

Back-up window met—was the data backed-up on time.

Restoration meeting Service Level Agreements (SLAs)—is data beingrestored according to SLA requirements.

Networking cost per unit storage—(the total cost of the communicationnetwork)×(the % of the communication network used by the system forstorage)÷(the storage units provided by the system).

% of storage cost for networking—networking costs divided by totalcosts.

The cost parameters for software costs are:

Average annual cost of software for disks—the yearly software cost fordisks.

Average annual cost of software for tape—the yearly software cost fortape.

Average annual cost of software for servers—the yearly software cost forservers.

% of storage cost for software—software costs divided by total costs.

The cost parameters for additional equipment costs are:

Annual Storage Area Network (SAN) equipment costs—the yearly cost forSAN equipment, such as SAN cabling and switches.

Annual network hardware costs—the yearly cost for networking hardware,such as blades, Network Attached Storage (NAS) filers, and other storageappliances.

Annual telecommunication costs—the yearly cost for telecom equipment andservices not included under networking costs.

Annual infrastructure costs—the yearly cost for floor space, racks, etc.

Other storage equipment costs—annual miscellaneous additional equipmentcosts not captured above.

% of storage cost for additional equipment—additional equipment costsdivided by total costs.

The cost parameters for environmental costs are:

Annual environmental costs—yearly cost for electricity, heating,lighting, cooling, etc.

Annual additional service related to storage—yearly cost ofmiscellaneous environmental services.

Annual business continuity costs—yearly loss due to environmentaldowntime.

% of storage cost for environment—environmental costs divided by totalcosts.

The cost parameters for outage costs are:

Average availability—the % of time that data is available from thesystem.

Average time that the availability covers—the time in hours, days, weeksduring which the availability is provided.

Availability being met—indicates if the promised availability wasdelivered by the system.

Hourly revenue loss for unscheduled outages—lost revenue (i.e. sales)per hour for unscheduled outages.

Hourly revenue loss for scheduled outages—lost revenue (i.e. sales) perhour for scheduled outages.

Hourly productivity loss for unscheduled outages—lost productivity (i.e.FTE hours) per hour for unscheduled outages.

Hourly productivity loss for scheduled outages—lost productivity (i.e.FTE hours) per hour for scheduled outages.

Average number of users affected by unscheduled outages—the typicalnumber of users impacted by unscheduled outages.

Average number of users affected by scheduled outages—the typical numberof users impacted by scheduled outages.

Outage penalties—cost penalties (i.e. in SLAs) attributed to outages.

Average hourly cost of outages—the average lost revenue and productivityper hour for scheduled and unscheduled outages.

Average annual hours of outages—average hours of outages per year.

Annual additional lost revenue or productivity—costs for outages notcaptured above.

% of storage costs for outages—outage costs divided by total cost.

The cost parameters for growth costs are:

Annual disk capacity growth—the yearly increase in disk storage dividedby total disk storage.

Annual tape capacity growth—the yearly increase in tape storage dividedby total tape storage.

Annual FTE growth—the yearly increase in the number of FTEs divided bytotal

FTEs.

Annual FTE burden growth—the yearly increase in FTE costs disk storagedivided by total FTE costs.

Annual server growth—the yearly increase in the number of serversdivided by total servers.

% of storage cost for growth—growth costs divided by total costs.

The cost parameters for financial assumptions are:

Corporate interface costs—the cost to interface with corporateexecutives and justify capital expenses.

Number of years for business case—the number of years for a return oninvestment in the business case.

Annual reduction in hardware costs—estimate of the percent reduction inhardware costs.

Inflation rate—estimate of the annual inflation rate.

Network management system 114 processes the above information toindicate total costs per unit storage ($/GB) for each computer systemand server system on GUI 1000. Network management system 114 alsoprocesses the above information to indicate comments for each computersystem and server system on GUI 1000.

For example, network management system 114 can calculate cost per unitof storage (GB) per system as follows.Cost per unit storage=cost of computer or storage system÷the datacapacity of the computer or storage system.

Network management system 114 can calculate the various data capacitieson a per system basis as follows.Storage capacity=total capacity of external disks+total capacity ofinternal disks+total capacity of tape.

Network management system 114 can calculate the various costs on a persystem basis as follows.Total system cost=FTE costs+server costs+internal disk costs+externaldisk costs+tape costs+network costs+software costs+additional equipmentcosts+environmental costs+outage costs+growth costs; whereFTE costs=(number of primary FTEs×primary FTE cost)+(number of secondaryFTEs×secondary FTE cost)+service contract costs.Server costs=(number of servers×% of small servers×average cost of smallservers)+(number of servers×% of medium servers×average cost of mediumservers)+(number of servers×% of large servers×average cost of largeservers).Internal disk costs=total cost for internal disks.External disk costs=(total GB of external disks×cost per GB for externaldisks)+disk configuration fees+disk maintenance fees.Tape costs=tape hardware cost+tape vaulting cost+tape media cost.Network costs=total network cost×% of network used for storage.Software costs=software cost for disks+software cost for tape+softwarecost for servers.Additional equipment costs=SAN equipment cost+network hardwarecost+telecommunication cost+infrastructure cost+storage equipment cost.Environmental cost=environmental cost+miscellaneous cost.Outage cost=average hourly cost of outages×annual hours per year ofoutages.Growth costs=(% disk growth×total disk capacity×average cost ofdisks)+(% server growth×total servers×average cost of server)+(% tapegrowth×total tape capacity×average cost of tape hardware, media, andvaulting)+(% FTE growth×total FTEs×average burdened cost of FTE).

Advantageously, network management system 114 provides a detailed costmodel that is broken down by computer and storage system. By using thecost per gigabyte calculations, the operator may directly compare thecost effectiveness of the various systems.

Storage Infrastructure Employee Model

Storage infrastructure 110 includes numerous storage systems 111-113that include disks, tape, and other memory devices and media. Storageinfrastructure 110 includes numerous computer systems, such as servers,that form a part of storage interfaces 103 and provide I/O to thestorage systems 111-113. Storage infrastructure 110 requiresemployees—referred to as Full Time Employees (FTEs)—to plan, design, andoperate the storage infrastructure. This entails planning, designing,and operating the computer systems and storage systems that comprise thestorage infrastructure. The FTEs execute various processes to performthese tasks.

Network management system 114 manages the FTEs associated with storageinfrastructure 110 in some examples of the invention. To accomplish thistask, network management system 114 interacts with an operator throughits GUI to develop individual FTE models for the individual computersystems and storage systems that comprise storage infrastructure 110. Inaddition, network management system 114 interacts with the operatorthrough the GUI to develop individual FTE models for the planning,design, and operation of storage infrastructure 110. Advantageously, themodels indicate FTE use at the process level as correlated to thecomputer systems, storage systems, and activities related to planning,design, and operation.

FIGS. 14-15 illustrate GUI 1400 that is provided by network managementsystem 114 to manage FTEs. The left column of GUI 1400 lists variousprocesses performed by the FTEs. The top row lists the computer andstorage systems although the number depicted is restricted for clarity,numerous other computer and storage system could be added to the toprow. Beneath each system are columns for planning, design, operations,and other activities. Planning activities relate to the development of astrategic plan for the infrastructure. Design activities relate to thedevelopment of detailed designs to implement the infrastructure plan.Operational activities relate to running the infrastructure asimplemented. The other column is for activities that are not primarilyrelated to planning, design, or operations. The percent of FTE time thatis spent on a given activity in the performance of a given process for agiven system is entered into the corresponding field.

In some cases, the operator may directly enter data for a given field.In other cases, the operator may position the GUI cursor over a field,and a drop down menu box appears with the various values for selection.The operator may position the cursor over the selected value forautomatic entry of the selected value into the field. In yet othercases, network management system 114 may retrieve the value from anothersystem or calculate the value from other inputs. For example, a timemanagement system may be used to track employee time by project oractivity, and network management system 114 may retrieve some valuesfrom the time management system. Thus, GUI 1400 is filled withinformation on a per process, per system, and per activity basis.Network management system 111 then processes the information to providea model that compares FTE usage across systems and activities at theprocess level.

The processes in the left column are: satisfy customer relationships,provide management system, manage business value, realize solutions,deploy solutions, deliver operational services, support networkservices, and manage network assets and infrastructure. Each of theseprocesses has a set of sub-processes. The processes and theirsub-process are described as follows:

Satisfy Customer Relationships—provide an interface to storagecustomers.

Understand customer requirements—interact with the customer to developgeneral customer needs.

Market storage services to customers—inform the customer about storageservices.

Administer storage service levels for customers—verify that storageservices meet customer Service Level Agreements (SLAs).

Provide operational support to customers—provide customer training,respond to customer questions and comments.

Manage customer satisfaction—interact with the customer to detectproblems and verify customer satisfaction.

Provide Management System—develop a management organization andprocesses.

Establish management framework—identify management roles andresponsibilities.

Define management processes and organization—specify how management iscarried out and who will perform the processes.

Evaluate management system—monitor and report on managementeffectiveness.

Manage Business Value—develop storage infrastructure to provide storageservices on a cost-benefit basis.

Understand costs and value—analyze the return on investment for storageinfrastructure development and storage service offerings.

Research storage technology—investigate new storage technologies andproducts.

Develop storage strategy—document guiding principles for the storageinfrastructure.

Develop and justify storage services—specify basic storage services andperform a cost benefit analysis for the services.

Define storage architecture—develop an infrastructure plan to providethe storage services according to the storage strategy.

Monitor storage services—analyze on-going return on investment for thestorage services.

Realize Customer Solutions—develop specific solutions for customers.

Understand solution requirements—develop a detailed set of customerneeds.

Design solutions—develop solutions to requirements and identify servicesto provide solutions.

Implement and integrate solutions—integrate and customize services toprovide solutions.

Test solutions—verify solutions are effective.

Certification and customer satisfaction—obtain necessary industrycertifications and ensure customer satisfaction for solutions.

Deploy Solutions—configure the storage infrastructure to provide thecustomer solutions.

Define infrastructure change management policies—specify standards forchanging infrastructure configuration.

Plan deployment for infrastructure change—develop a deployment plan forthe infrastructure change.

Administer infrastructure change—manage the deployment plan.

Implement infrastructure change—execute the deployment plan.

Deliver Operational Services—operate the storage infrastructure.

Define service delivery plan—develop an operational plan for theinfrastructure.

Allocate storage resources—provide resources to execute the operationalplan.

Collect performance and utilization data—monitor and reportinfrastructure performance.

Perform maintenance—perform tasks to maintain the infrastructure.

Support Network Services—provide operational management for theinfrastructure

Manage configuration information—provide a secure configuration datarepository.

Manage availability—verify that storage systems meet applicableavailability standards.

Manage facilities—provide appropriate operating environment.

Manage back-up and recovery—verify that scheduled back-up and recoveryoperations occur properly.

Manage service continuity—verify that unscheduled back-up and recoveryoperations occur properly.

Manage performance and capacity—verify that infrastructure performanceand capacity are meeting plans and designs.

Manage problems—provide resources to intake, investigate, and resolveproblems.

Manage Network Assets and Infrastructure—provide executive managementfor the infrastructure.

Manage finance—provide accounting and finance control.

Manage procurement—control product and service purchases.

Set pricing and administer customer contracts—establish pricing andnegotiate customer agreements.

Manage storage inventory and assets—ensure inventory and assets arehandled properly.

Manage security—provide a secure environment for the infrastructure.

Manage human resources—manage employees

Manage skills portfolio and provide training—maintain appropriate skillsets at the organizational and individual levels.

Thus, GUI 1400 lists the percent of FTE time that is spent on variousprocesses and sub-processes as correlated to various activities forvarious systems. Network management system 114 processes the informationon GUI 1400 to provide various totals. Note that process sub-total rowsprovide sub-totals for each process, and the bottom row provides totalsfor all processes. The right column provides totals for each process andsub-process for all systems and activities. Advantageously, networkmanagement system 114 provides a direct comparison of how FTE time isspent on various processes and systems.

Storage Infrastructure Inventory Model

Storage infrastructure 110 includes numerous storage systems 111-113that include disks, tape, and other memory devices and media. Storageinfrastructure 110 includes numerous computer systems, such as servers,that form a part of storage interfaces 103 and provide I/O to thestorage systems 111-113. Thus, storage infrastructure 110 includesnumerous devices and systems that are comprised various vendor products.The vendor products represent an asset inventory that must be managed.

Network management system 114 manages the inventory that comprisesstorage infrastructure 110 in some examples of the invention. Toaccomplish this task, network management system 114 interacts with anoperator through its GUI to develop an inventory model for storageinfrastructure 110. Advantageously, the inventory model indicatesinventory assets and characteristics of interest. In some cases, theassets are storage systems, such as disk and tape systems.

FIG. 16 illustrates GUI 1600 that is provided by network managementsystem 114 to manage inventory. The top row left column of GUI 1600lists various inventory assets that comprise storage infrastructure 110.The left column lists various characteristics for each asset. The assetcharacteristics are indicated below.

Vendor—indicates the supplier of the product.

Operating Systems—indicates compatible operating systems.

Location—identifies the physical site having the asset.

Storage Type—identifies the asset by storage type, such as networkattached storage, storage area network, tape, etc.

Number of servers—the number of servers connected to the asset.

Number of connections—the number of connections from the servers to theasset.

Owned or leased—is the asset owned or leased.

% depreciated (if owned)—the age of the asset divided by theamortization term for the asset.

Charge per month (if leased)—the monthly lease payment.

Acquisition cost—the cost to obtain the asset

Acquisition data—the date the asset was acquired.

Depreciation term—the amortization period for the asset.

Maintenance contract—is there a maintenance contract.

Maintenance cost per year—annual maintenance cost.

Number of months installed—the elapsed time since installation.

Maximum capacity—maximum storage capacity of the asset.

Installed capacity—installed storage capacity of the asset.

Hot spare capacity—hot spare capacity available from the asset.

Available capacity—storage capacity available from the asset.

Utilized capacity—% of available storage capacity in use in the asset.

RAID level—the industry standard RAID level of the asset.

In some cases, the operator may directly enter data for a given field.In other cases, the operator may position the GUI cursor over a field,and a drop down menu box appears with the various values for selection.The operator may position the cursor over the selected value forautomatic entry of the selected value into the field. In yet othercases, network management system 114 may retrieve the value from anothersystem or calculate the value from other inputs. For example, manyassets can report their current capacity to network management system114 by using over Simple Network Management Protocol (SNMP). Thus, GUI1600 is filled with information on a per asset basis. Network managementsystem 110 then processes the information to provide a model thatcompares assets in terms of maximum, installed, available, and in-usestorage capacities.

FIGS. 17-19 illustrate GUI 1700 that is provided by network managementsystem 114 to manage inventory. GUI 1700 depicts a block diagram ofstorage infrastructure 110 that includes storage interfaces 103, tieredstorage systems 111-113, and network 120. The GUI operator may selectone of these elements, such as by clicking the element with a mouse, andGUI 1700 depicts the selected element in further detail. This operatorselection process can continue until desired product or statusinformation is provided.

For example, the GUI operator may select tier 2 storage system 112 asindicated by the “X” mark on FIG. 17. In response to the selection oftier 2 storage system 112, GUI 1700 depicts tier 2 storage system 112 infurther detail as shown in FIG. 18. On FIG. 18, GUI 1700 shows tier 2storage system 112 as having computer systems 1-N and disk systems 1-N.The GUI operator may then select disk system 1 as indicated by the “X”mark on FIG. 18. In response to the selection of disk system 1, GUI 1700depicts disk system 1 in further detail as shown in FIG. 19. On FIG. 19,GUI 1700 shows disk system 2 as having disks 1-N. The GUI operator mayfinally select disk 2 as indicated by the “X” mark on FIG. 19. Inresponse to the selection of disk 2, GUI 1700 depicts product and statusinformation for disk 2 in an information box as shown in FIG. 19. Theinformation box indicates information for disk 2 including: product ID,vendor, location, installation date, total capacity, and unusedcapacity. Note that other information, such as that indicated on FIG.16, could be included in information box 1900.

The above example could be repeated for other elements of storageinfrastructure 110. The GUI operator could have selected storageinterfaces 103, and made additional selections until information forspecific product in storage interfaces 103 is provided. For example, GUI1700 could be used to obtain product information for a storage switch instorage interfaces 103. In a similar fashion, GUI 1700 could be used toobtain product information for a network link in communication network120.

Storage Infrastructure Funding

Network management system 114 manages storage infrastructure funding insome examples of the invention. To accomplish this task, networkmanagement system 114 interacts with an operator through its GUI toprovide project funding and scheduling information. FIGS. 20-22illustrate GUI 2000 that is provided by network management system 114 tomanage funding.

On FIG. 20, the left two columns of GUI 2000 lists various projects byID and name. The third column lists the roll-out date for the project,where the roll-out date indicates when project funding must beavailable. The fourth column lists the total budget for each project.This project information could be entered by the operator or retrievedfrom other management systems.

Network management system 114 processes the project information todetermine the preliminary storage budget for the project, savingsprovided by storage infrastructure 110, and a final storage budget. Todetermine this information, network management system 114 can applyvarious rules to the project data. For example, the preliminary storagebudget could be a percentage of the total budget, where the percentagecould be based on the total budget cost as follows.

TOTAL STORAGE BUDGET BUDGET PERCENTAGE 0 to $500 K 20% $500 K to $1 M25% $1 M to $3 M 30% $3 M to $5 M 35% $5 M to $10 M 40%

The preliminary storage budget would be the total budget multiplied bythe appropriate percentage. Note that other techniques or factors couldbe used. For example, the percentages could be further broken down basedon the type of project, the organization handling the project, or someother factor.

The savings provided by storage infrastructure 110 can be a percentageof the preliminary storage budget, where the percentage could be basedon the preliminary storage budget as follows.

PRELIMINARY STORAGE SAVINGS BUDGET PERCENTAGE 0 to $500 K  5% $500 K to$1 M 10% $1 M to $3 M 15% $3 M to $5 M 20% $5 M to $10 M 25%

The storage savings would be the preliminary storage budget multipliedby the appropriate percentage. Note that other techniques or factorscould be used. For example, the percentages could be further broken downbased on the type of project, the organization handling the project, orsome other factor. The final storage budget is the preliminary storagebudget less the savings.

Note that the budget numbers could be further broken down into subjectmatter buckets. For example, the final storage budget for a projectcould be separated into a hardware budget, software budget, and servicesbudget by using a rule set. For example, the final storage budget couldbe allocated as follows: 60% of the final storage budget is forhardware, 20% is for software, and 20% is for services.

FIG. 21 shows another version of GUI 2000. GUI 2000 now provides afuture forecast of storage funding based on the data of FIG. 20. On FIG.21, the vertical axis represents storage funding and the horizontal axisrepresents time from the present in months. The final storage budget foreach project is added to the total storage budget as of the roll-outdate. In this example, the present time for GUI 2000 is Jan. 1, 2006 sothe $450 K final storage budget for project X1 appears after the firstmonth. The $1M final storage budget for project X3 and the $2.4 M finalstorage budget for projects X3 and X4 appear after the fifth month.

FIG. 22 shows another version of GUI 2000. GUI 2000 now provides a graphof actual storage investment and savings based on actual spending andsavings data. The actual numbers could be retrieved from an accountingsystem. On FIG. 22, the vertical axis represents monetary amounts foractual storage investment and savings. The horizontal axis representstime periods in the past broken down by quarter, although other timeperiods such as months could be used. For each quarter, bar graphsindicate investment in the quarter, savings in the quarter, totalinvestment for the specified period, and total savings for the specifiedperiod. From FIG. 22, it can be seen that the total investment andsavings bars grow at the rate of quarterly investment and savings.

The operator may select which version of GUI 2000 (FIG. 21, 22, or 23)to view through the use of selection buttons, page tabs, or some otherGUI technique. Advantageously, the operator is automatically providedwith a financial picture of the storage infrastructure that indicatespast, present, and future investment and savings. This information is ofcritical importance when making decisions on funding and timing of newstorage projects and when evaluating existing projects.

Application Status and Implementation Information

Network management system 114 manages storage infrastructure applicationstatus in some examples of the invention. To accomplish this task,network management system 114 interacts with an operator through its GUIto provide application status and implementation information.

FIG. 23 illustrates GUI 2300 that is provided by network managementsystem 114 to manage application status. On FIG. 23, variousapplications 1-N and their respective data flows 1-N are shown at thetop of GUI 2300. The various information classes, service classes, andstorage system tiers are shown under the applications on GUI 2300. Inresponse to the selection of a specific data flow for a givenapplication, GUI 2300 graphically illustrates the information class,service class, and storage tier for the selected data flow.

For example on FIG. 23, the operator has selected data flow #1 ofapplication #2 on GUI 2300 as indicated by the “X” mark. In response tothe selection, GUI 2300 uses arrows to illustrate that the selected dataflow has been assigned to information class #2, service class #3, andstorage tier #2. Note that color coding or other graphical techniquescould be used to simultaneously illustrate these assignments formultiple data flows.

FIGS. 24-26 illustrates GUI 2400 that is provided by network managementsystem 114 to manage application implementation information. On FIGS.24-26, various applications 1-N and their respective data flows 1-N areshown at the top of GUI 2400. The various storage interfaces and storagetiers are shown under the applications on GUI 2400. The top of GUI 2400also has selection buttons for various views that show the variousstages of implementation. The views are for planned implementations,implementations under test, and operational implementations.

In response to the selection of planned implementations (as indicated bythe “X” mark on FIG. 24), GUI 2400 graphically illustrates theapplications, data flows, storage interfaces and storage tiers that areplanned but not yet tested or operational. In this example, a dashedline is used to indicate that applications 2-N (and their data flows),storage interfaces 3-N, and storage tier N are planned but not yettested or operational.

In response to the selection of implementations under test (as indicatedby the “X” mark on FIG. 25), GUI 2400 graphically illustrates theapplications, data flows, storage interfaces, and storage tiers that areunder test but not yet operational. In this example, a dashed line isused to indicate that storage interface 2 and storage tiers 2-3 arecurrently under test.

In response to the selection of operational implementations (asindicated by the “X” mark on FIG. 26), GUI 2400 graphically illustratesthe applications, data flows, storage interfaces and storage tiers thatare operational—meaning that planning and testing is complete. In thisexample, a dashed line is used to indicate that application #1, storageinterface #1, and storage tier #1 are currently operational. Note thatcolor coding or other graphical techniques could be used tosimultaneously illustrate the implementations that are planned, undertest, and operational.

Network management system 114 could retrieve the current status of thevarious applications and systems from another system, or the operatorcould enter the status for each application and system. Advantageously,network management system 114 enables the GUI operator to obtain a quickbut effective view of the planning and development of storageinfrastructure 110.

Storage Management System

FIGS. 1-26 and the preceding text have described storage managementsystem 114 that manages storage infrastructure 110 in communicationnetwork 100. Storage management system 114 assigns individual data flowsto individual storage systems 111-113 based on a rigorous and robustanalysis. Storage management system 114 also displays data storageinfrastructure 110 and various related information. Storage managementsystem 114 displays infrastructure models, implementation status, andfunding status for data storage infrastructure 110. The models include acost model, an employee model, and an inventory model. Theimplementation status indicates if systems in data storageinfrastructure 110 are planned, under test, or operational. The fundingstatus indicates actual past funding and forecasted future funding.Storage management system 114 also determines gaps between the currentstorage infrastructure and a target storage infrastructure. The gapsinclude a personnel gap, a hardware gap, and a software gap.

Advantageously, storage management system 114 provides a powerfulmanagement tool for storage infrastructures in communication networks.Storage management system 114 tracks and models current infrastructurestatus, identifies gaps for infrastructure growth, analyzesinfrastructure funding, and assigns new data flows to the proper storagesystem and service level. Thus, storage management system 114 provides acomprehensive set of capabilities that address numerous problems facingcommunication networks that require complex storage infrastructures.

1. A data storage infrastructure for a communication network thatproduces a plurality of data flows of network data, the data storageinfrastructure comprising: a plurality of data storage systemsconfigured to store the network data, wherein each one of the datastorage systems comprises a storage system tier of a plurality ofstorage system tiers; and a storage management system configured toidentify characteristics for the data flows, score the characteristicsfor the data flows resulting in scores for the data flows, sum thescores to generate total scores for the data flows, and identify keyvariables for the data flows to determine a compatibility between eachone of the data flows and a plurality of classes of service, wherein theclasses of service comprise extremely critical, mission critical,business critical, and back-office, and wherein the key variablescomprise access frequency, availability, policy enforcement, geographicdiversity, business impact if data is lost, monitoring requirements,response time, and whether the network data is required forestablishment and operation of communication paths for customers; andthe storage management system further configured to select a class ofservice of the plurality of classes of service for each one of the dataflows based on the total score and the key variables identified for eachone of the data flows, and select one of the storage system tiers foreach one of the data flows based on the selected class of service,wherein the data storage systems are configured to store the data flowsin the selected ones of the storage system tiers.
 2. The data storageinfrastructure of claim 1 wherein the different ones of the data storagesystems have different data storage reliabilities.
 3. The data storageinfrastructure of claim 1 wherein the storage management system isconfigured to normalize the scores.
 4. The data storage infrastructureof claim 1 wherein the storage management system is configured to weightthe scores for the individual data flows.
 5. The data storageinfrastructure of claim 1 wherein the characteristics indicate users ofthe data flows.
 6. The data storage infrastructure of claim 1 whereinthe characteristics indicate monetary values of the data flows.
 7. Thedata storage infrastructure of claim 1 wherein the characteristicsindicate priorities of the data flows.
 8. The data storageinfrastructure of claim 1 wherein the characteristics indicatelife-cycles of the data flows.
 9. The data storage infrastructure ofclaim 1 wherein the characteristics indicate legal compliancerequirements of the data flows.
 10. The data storage infrastructure ofclaim 1 wherein the characteristics indicate performance requirements ofthe data flows.
 11. A method of operating a data storage infrastructurefor a communication network that produces a plurality of data flows ofnetwork data, the method comprising: in a plurality of data storagesystems, storing the network data, wherein each one of the data storagesystems comprises a storage system tier of a plurality of storage systemtiers; and in a storage management system, identifying characteristicsfor the data flows, scoring the characteristics for the data flowsresulting in scores for the data flows, summing the scores to generatetotal scores for the data flows, and identifying key variables for thedata flows to determine a compatibility between each one of the dataflows and a plurality of classes of service, wherein the classes ofservice comprise extremely critical, mission critical, businesscritical, and back-office, and wherein the key variables comprise accessfrequency, availability, policy enforcement, geographic diversity,business impact if data is lost, monitoring requirements, response time,and whether the network data is required for establishment and operationof communication paths for customers; and in the storage managementsystem, selecting a class of service of the plurality of classes ofservice for each one of the data flows based on the total score and thekey variables identified for each one of the data flows, and selectingone of the storage system tiers for each one of the data flows based onthe selected class of service, wherein the data storage systems storingthe network data comprises the data storage systems storing the dataflows in the selected ones of the storage system tiers.
 12. The methodof claim 11 wherein the different ones of the data storage systems havedifferent data storage reliabilities.
 13. The method of claim 11 furthercomprising, in the storage management system, normalizing the scores.14. The method of claim 11 further comprising, in the storage managementsystem, weighting the scores for the individual data flows.
 15. Themethod of claim 11 wherein the characteristics indicate users of thedata flows.
 16. The method of claim 11 wherein the characteristicsindicate monetary values of the data flows.
 17. The method of claim 11wherein the characteristics indicate priorities of the data flows. 18.The method of claim 11 wherein the characteristics indicate life-cyclesof the data flows.
 19. The method of claim 11 wherein thecharacteristics indicate legal compliance requirements of the dataflows.
 20. The method of claim 11 wherein the characteristics indicateperformance requirements of the data flows.